Walkthrough

Adds dev-mode wallet impersonation to connect context, extends RecipientSelector with profile/wallet rendering flags, implements dual minting flows (mint-for-fren vs mint-for-me) in ManifoldMintingConnect, adds mint diagnostics UI in ManifoldMintingWidget, and introduces tests for wallet/profile switching during mint flows.

Changes

Sequence Diagram

sequenceDiagram
    participant User as User
    participant Connect as SeizeConnectContext
    participant Mint as ManifoldMintingConnect
    participant Selector as RecipientSelector
    participant Callback as onMintFor

    User->>Connect: (optionally) enable DEV impersonation / connect wallet
    Connect-->>Mint: provide `address`, `isConnected`, `isAuthenticated`
    User->>Mint: Toggle "Mint for Fren" / "Mint for Me"
    alt Mint for Fren
        Mint->>Selector: render Fren profile & wallets
        User->>Selector: select Fren profile / wallet
        Selector-->>Mint: update Fren wallet state
        Mint->>Callback: invoke onMintFor(Fren wallet)
    else Mint for Me
        Mint->>Mint: reset Fren state, derive connected recipient
        Mint->>Selector: render connected profile (profile-change disabled)
        User->>Selector: select connected wallet (if multiple)
        Selector-->>Mint: update selected connected wallet
        Mint->>Callback: invoke onMintFor(connected wallet)
    end

Estimated Code Review Effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly Related PRs

• Minting freeze fix #1519: Modifies minting logic/UI in components/manifoldMinting/ManifoldMintingWidget.tsx, overlapping diagnostics and mint flow areas.
• Transfer NFTs #1528: Integrates TransferModalPfp and recipient selection changes referenced by updated minting components.

Suggested Reviewers

• simo6529
• ragnep

Poem

🐰 I hop between dev and main,
Two minting paths within my lane.
Fren or Me, a tiny hop,
Wallets chosen — never stop.
Carrots, code, and a joyful pop! 🥕

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

• 📝 Generate docstrings

components/auth/SeizeConnectContext.tsx (1)

368-376: Nit: consider memoizing the environment/hostname checks.

nodeEnv, isDevLikeEnv, and isLocalHost are recomputed every render but their values never change during the component's lifetime. Wrapping them in useMemo(() => ..., []) (or extracting them to module-level constants) would make the intent clearer and avoid repeated globalThis.window.location.hostname accesses.

♻️ Example: extract to module scope

+// Module-level constants (evaluated once)
+const IS_DEV_LIKE_ENV = (() => {
+  const env = getNodeEnv();
+  return env === "development" || env === "test" || env === "local";
+})();
+
+const IS_LOCAL_HOST =
+  typeof globalThis.window !== "undefined" &&
+  (globalThis.window.location.hostname === "localhost" ||
+    globalThis.window.location.hostname === "127.0.0.1" ||
+    globalThis.window.location.hostname === "::1" ||
+    globalThis.window.location.hostname.endsWith(".local"));
+
 export const SeizeConnectProvider: React.FC<{ children: React.ReactNode }> = ({
   children,
 }) => {
   // ...
-  const nodeEnv = getNodeEnv();
-  const isDevLikeEnv =
-    nodeEnv === "development" || nodeEnv === "test" || nodeEnv === "local";
-  const isLocalHost =
-    globalThis.window !== undefined &&
-    (globalThis.window.location.hostname === "localhost" ||
-      globalThis.window.location.hostname === "127.0.0.1" ||
-      globalThis.window.location.hostname === "::1" ||
-      globalThis.window.location.hostname.endsWith(".local"));
   const impersonatedAddress =
-    isDevLikeEnv &&
-    isLocalHost &&
+    IS_DEV_LIKE_ENV &&
+    IS_LOCAL_HOST &&
     publicEnv.USE_DEV_AUTH === "true" &&

components/manifoldMinting/ManifoldMintingWidget.tsx (2)

207-244: buildMintDiagnostics is also called during render — consider memoizing or deferring.

printMintDebug (line 558) calls buildMintDiagnostics() synchronously in the render path, which in turn calls getSelectedMerkleProofs(), getValue(), and conditionally getMintArgs(). Since this is gated behind isMintDebugEnabled, the impact is negligible in production — but when the flag is on, it re-runs every render cycle.

Not a blocker; just flagging for awareness.

---

246-256: setTimeout in finally isn't cleared on unmount.

If the component unmounts within the 2-second window, setCopyStatus("") will fire on an unmounted component. React 18+ no longer warns about this, but the stale call is still wasted work. Since this is debug-only tooling, it's low priority.

♻️ Optional cleanup with useRef

If you ever want to tighten this up:

+ const copyTimeoutRef = useRef<ReturnType<typeof setTimeout>>();
+ useEffect(() => () => clearTimeout(copyTimeoutRef.current), []);
  
  const onCopyMintDiagnostics = async () => {
    try {
      const diagnostics = buildMintDiagnostics();
      await navigator.clipboard.writeText(JSON.stringify(diagnostics, null, 2));
      setCopyStatus("copied");
    } catch {
      setCopyStatus("failed");
    } finally {
-     setTimeout(() => setCopyStatus(""), 2000);
+     copyTimeoutRef.current = setTimeout(() => setCopyStatus(""), 2000);
    }
  };

• X
• Mastodon
• Reddit
• LinkedIn